feat(security-agent): move manual workflows into workers#3312
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryAll commits reviewed — no new changes since the last review cycle. The PR is clean across 104 files covering the security-agent worker migration, auto-analysis orchestration, dismissal hardening, and the final nullable Dependabot schema fix. Files Reviewed (104 files — all clean)Latest commit (
Previously reviewed commits (101 files — all clean, carried forward)
Reviewed by claude-sonnet-4.6 · incremental review Reviewed by claude-4.6-sonnet-20260217 · 307,101 tokens Review guidance: REVIEW.md from base branch |
efac67d to
cc0b7fb
Compare
|
I'm noticing a growing number of services that use the I'd recommend doing what we do for the abuse service, which is to protect your worker with Cloudflare Access, create a Cloudflare Access Service Token for authenticating with that application, and share that specific token with the cloud service to authenticate with your worker. |
RSO
left a comment
There was a problem hiding this comment.
Still working on the review, but I'm pretty sure that this PR would leak the INTERNAL_API_TOKEN so I'm requesting changes already.
1d099b1 to
dc013c1
Compare
RSO
left a comment
There was a problem hiding this comment.
Approving, but with a PR of this size, I think it's fair to assume that something will break, so let's apply some caution when we merge it.
…tion Ensures that both the security finding status update and the audit log insertion are performed atomically, preventing inconsistent states if the audit log insertion fails.
2816e68 to
fd53415
Compare
Summary
Security Agent manual sync, dismissal, and analysis work now enter durable Worker-backed command paths, while callback delivery stays generic in Cloud Agent Next and finalization remains owned by Security Auto Analysis.
Why this change is needed
Manual Security Agent actions can trigger multi-step GitHub, queue, Cloud Agent, and callback work. Keeping that orchestration on synchronous web paths makes request latency, retries, ownership checks, and terminal state recovery harder to control. The security callback fast path also made
cloud-agent-nextaware of one product-specific downstream consumer, which blurred service boundaries.How this is addressed
cloud-agent-nextcallback delivery generic: callers provide ordinary HTTP callback targets, and Security Auto Analysis now configures Worker callback ingress while retaining the web route as rollback-compatible ingress.Architecture
Human Verification
Reviewer Notes
Human Reviewer Flags
cloud-agent-nextno longer knows about Security Auto Analysis delivery mode or service binding; callback destination ownership moves back to the caller.Code Reviewer Agent
Code Reviewer Notes
services/security-sync/src/dismiss.tsandservices/security-auto-analysis/src/manual-analysis.ts.services/cloud-agent-next/src/callbacks/delivery.tsplus Security Auto Analysis target construction inservices/security-auto-analysis/src/launch.ts.packages/worker-utils/src/security-auto-analysis-policy.tsandpackages/worker-utils/src/dependabot-dismissal-target.ts.